User interface data sample transformer

ABSTRACT

An approach for transforming a large dataset using user interface-based transformations applied to a sample of the dataset is disclosed. The sample of the large dataset has the same or similar format as the large dataset. A user can quickly apply transformations to the sample dataset using UI-based instructions. The UI-based instructions can be used to create a transformation job that can be configured to run on a backed database, such as a distributed database, to apply the transformations to the large dataset.

RELATED APPLICATIONS

This application is a continuation of Ser. No. 15/675,173, entitled“User Interface Data Sample Transformer,” filed on Aug. 11, 2017, whichclaims the priority benefit of U.S. Provisional Application No.62/495,587, entitled “User Interface Data Sample Transformer,” filed onAug. 17, 2016, which are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

The present disclosure generally relates to the technical field ofspecial-purpose machines that facilitate data manipulation andvalidation including computerized variants of such special-purposemachines and improvements to such variants, and to the technologies bywhich such special-purpose machines become improved compared to otherspecial-purpose machines that facilitate data manipulation andvalidation. In particular, the present disclosure addresses systems andmethods for user interface data sample based transformations of data.

BACKGROUND

In recent years, extremely large amounts of data have been generated bynetwork-connected systems and users. The collected data may containpatterns that show malicious online behavior, e.g., behavior by malwareor hackers, potential terrorism activities, potential sources of foodpoisoning, or even the best bike routes for a morning commute.Conventional data analysis tools have been unable to parse the extremelylarge amounts of data in human-understandable ways, thus the patternsremain hidden, e.g., signals lost in noise. Worse yet, much of theextremely large amounts of data is in an unstructured form whichconventional data analysis tools cannot parse. Users attempting to addstructure to the data encounter various types of errors, includingprogram freezing and crashing. As is evident, there is a demand forimproved approaches for structuring and analyzing extremely large setsof data.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and should not be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating a network-based data analysissystem for a user interface (UI) sample dataset-based transformation ofdata, according to some example embodiments.

FIG. 2 is a block diagram illustrating example components forming partof a UI sample transformer, according to some example embodiments.

FIG. 3 is a flow diagram illustrating a method of transforming largesets of data using a UI sample-based approach, according to some exampleembodiments.

FIG. 4 is a flow diagram illustrating a method of transforming newlyreceived large sets of data using a pre-generated transformation job andvalidation, according to some example embodiments.

FIG. 5 is a flow diagram illustrating a method of analyzing the originaland newly received data, according to some example embodiments.

FIGS. 6A-6E illustrate example user interfaces for sample dataset-basedtransformation of large sets of data, according to some exampleembodiments.

FIG. 7 is a network interaction diagram illustrating sample-basedtransformation of large datasets in a network environment, according tosome example embodiments.

FIG. 8 illustrates a diagrammatic representation of a machine in theform of a computer system within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, according to an example embodiment.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

In various example embodiments, raw data can be imported and transformedusing a sample portion of the raw data. The raw data may be unstructuredor structured data. The transformations may define structure for the rawdata, change pre-existing structure (e.g., schema) of the data, add orremove portions of the data, modify the data values, or modify datatypes assigned to data values in the raw data. To apply transformations,a sample portion of the raw data is displayed in a UI with a controlmenu. The control menu includes one or more transformation elements(e.g., buttons, drop-downs, fields) that are configured to applytransformations to the raw data. The transformations are applied to thesample portions of the data in real time or near real time, withoutapplying the transformations to the raw data not in the sample. In thisway, by applying each transformation only to the sample displayed in theUI, the user can see the changes applied to the sample and judge whetherthe transformations were applied properly and further determine whetheradditional transformations are need to further transform the raw datainto structured data.

Once the user determines that no more transformations are necessary, thetransformations are recorded as a transformation job that can be appliedto the rest of the raw data (e.g., the raw data not included in thedisplayed sample set) stored in a backend database. The transformationson the rest of the raw data transform the raw data into a structuredform per the transformation job recorded from the sample datasettransformations.

When newer raw data (e.g., raw data in the same raw unstructured format)is received, the transformation job is automatically applied to the newraw data, and stored with the structured data in the database backend.The newer raw data may comprise entirely new values in raw format orupdates to the data already transformed and stored in a backenddatabase. In some embodiments, the transformations specify types ofvalidations to occur when transforming the data (e.g., exclude dataoutside a defined range of values, make sure a given column containsonly integers). If, during the transformations, an error occurs due toone or more validations failing, an error message is generated; the usercan ignore the error message, correct the error manually, or create anew transformation task to address future errors of the same type.

In this way, a user can effectuate transformations to arbitrarily largedatasets (e.g., trillions of rows, thousands of columns) through a fastand responsive UI-based approach that shows the results of thetransformations in real time and uses a transformation job to transformraw data into a structured form ready for analysis.

With reference to FIG. 1, an example embodiment of a high-levelclient-server-based network architecture 100 is shown. A network-baseddata analysis system 104 provides server-side functionality via anetwork 102 (e.g., the Internet or wide area network (WAN)) to one ormore client devices 106 and 108. In some implementations, a dataarchitect user (e.g., user 196) interacts with the network-based dataanalysis system 104 using the client device 106, and an analyst user(e.g., user 198) interacts with the network-based data analysis system104 using client device 108. The data visualizer application 128 is anapplication to import, transform, and visualize data. For example, user196 can use the data visualizer application 128 to import raw data andtransform it for storage and later analysis. Further, user 198 can usethe data visualizer application 128 to view the data transformed peruser 196. In some embodiments, the data visualizer application 128 isrun as local software executed by processors of the client device (e.g.,client device 106 and client device 108). In some embodiments, the datavisualizer application 128 is run from a web client (e.g., a browser) asa cloud service that works with application server 118 to provide cloudservices (e.g., cloud-based data analysis).

In various implementations, the client devices 106 and 108 each comprisea computing device that includes at least a display and communicationcapabilities that provide access to the network-based data analysissystem 104 via the network 102. The client device can be implemented as,but is not limited to, a remote device, work station, Internetappliance, hand-held device, wireless device, portable device, wearablecomputer, cellular or mobile phone, Personal Digital Assistant (PDA),smart phone, tablet, ultrabook, netbook, laptop, desktop,multi-processor system, microprocessor-based or programmable consumerelectronic, game consoles, set-top box, network Personal Computer (PC),mini-computer, and so forth.

In some embodiments, the data visualizer application 128 accesses thevarious systems of the network-based data analysis system 104 via theweb interface supported by a web server 122. Similarly, in someembodiments, the data visualizer application 128 can initiate tasks tobe performed programmatically (e.g., automatically) without user input.In those example embodiments, the data visualizer application 128 caninterface to perform the programmatic tasks through an ApplicationProgram Interface (API) server 114 located on the server side (e.g.,within network-based data analysis system 104).

Users (e.g., the user 196 and 198) comprise a person, a machine, orother means of interacting with the client devices (e.g., client device106 and 108). In some example embodiments, the user is not part of thenetwork architecture 100, but interacts with the network architecture100 via the client devices 106 and 108. For instance, the user 196provides input (e.g., touch screen input or alphanumeric input) to theclient device 106 and the input is communicated to the network-baseddata analysis system 104 via the network 102. In this instance, thenetwork-based data analysis system 104, in response to receiving theinput from the user 196, communicates information from applicationserver 118 to the client device 106 via the network 102 to be presentedto the user 196. In this way, according to some example embodiments,users can interact with the network-based data analysis system 104 usingtheir respective client devices.

As illustrated in the example embodiment of FIG. 1, the API server 114and the web server 122 are coupled to, and provide programmatic and webinterfaces respectively to, one or more application server 118. Theapplication server 118 can host a UI sample transformer 124 configuredto receive raw data, and perform transformations on a sample of the rawdata to record as a transformation job. As described in further detailbelow, the UI sample transformer 124 may create a sample of the raw datafor display on data visualizer application 128 for transformation jobgeneration. The portion of the raw data not included in the sample isstored in a database system (e.g., database backend), such as databasesystem 120. In some example embodiments, the raw data not in the samplecan be distributed across data stores 122A-N, which are configured towork as distributed data stores for a distributed database system.

In some example embodiments, the database system 120 is implemented asan Apache Hadoop-based system, which may implement Hadoop techniques(e.g., MapReduce) on Hadoop Distributed File System (HDFS) datastores,such as data stores 122A-N. It is appreciated that Hadoop and HDFS aremere examples of the database system 120 and features and fileimplementations may be modified. For example, in some embodiments, thedata stores 122A-N are HDFS formatted files which can be transformedusing Apache Spark functionality that is integrated into UI sampletransformer 124.

FIG. 2 illustrates a block diagram showing components provided withinthe UI sample transformer 124, according to some example embodiments. Asis understood by skilled artisans in the relevant computer andInternet-related arts, each functional component (e.g., engine, module,or database) illustrated in FIG. 2 may be implemented using hardware(e.g., a processor of a machine) or a combination of logic (e.g.,executable software instructions) and hardware (e.g., memory andprocessor of a machine) for executing the logic. Furthermore, thevarious functional components depicted in FIG. 2 may reside on a singlemachine (e.g., a server) or may be distributed across several machinesin various arrangements such as cloud-based architectures. Moreover, anytwo or more of these components may be combined into a single component(e.g., a single module), and the functions described herein for a singlecomponent may be subdivided among multiple modules.

As illustrated in FIG. 2, the UI sample transformer 124 comprisesmultiple engines that implement data transformation of raw data intostructured data, according to some example embodiments. The componentsthemselves are communicatively coupled (e.g., via appropriateinterfaces) to each other and to various data sources, so as to allowinformation to be passed between the applications or so as to allow theapplications to share and access common data. Although in FIG. 2components, such as the transformation engine 205, are displayed withinthe UI sample transformer 124 on the server side, in some embodiments,one or more components of the UI sample transformer 124 may beintegrated into a client-side program (e.g., data visualizer application128) to improve responsiveness. To this end, the UI sample transformer124 comprises an interface engine 200, a transformation engine 205, arecord engine 210, a database engine 215, an analysis engine 220, and avalidation engine 225.

The interface engine 200 manages generating and displaying userinterfaces on the client devices 106 and 108 using the data visualizerapplication 128. In particular, the interface engine 200 generates a UIdisplay of a sample dataset of data to be imported and control elementsthat can be manipulated by the user to effectuate changes to thedisplayed sample dataset. The transformation logic is provided bytransformation engine 205, which is configured to receive specifictransformation commands from the UI, apply the transformation commandsto the sample dataset, and pass the resultant transformed data to theinterface engine 200, which then transmits the resultant transformeddata to the client device for display by the data visualizer application128. How the transformations are applied and example types oftransformations are discussed in further detail below, with reference toFIGS. 6A-6E.

In some example embodiments, the transformation engine 205 is located inthe data visualizer application 128 and transformations are implementedby the client-side transformation engine 205 using a client sideprogramming language (e.g., browser-executable code type, browserexecuted JavaScript, code executed locally by client device 106), whichallow the user to quickly see the changes he/she is making to the sampledataset in real time or near real time, without waiting for thetransformations to be applied to the full raw dataset, which may be manypetabytes in size.

The record engine 210 is configured to record the appliedtransformations (e.g., types of transformations applied, and order oftransformations applied) to the sample dataset. As with thetransformation engine 205, in some embodiments, the record engine 210 isintegrated into the data visualizer application 128 to recordclient-side transformations applied to the sample dataset. Upon a buildcommand being selected, the record engine 210 uses the selectedtransformations to generate a transformation job, which is thentransmitted to the UI sample transformer 124. The UI sample transformer124 then applies the transformation job to the rest of the raw datastored in the database system 120.

In some embodiments, the record engine 210 is configured to generate thetransformation job into a database-executable code type that executesacross a distributed data storage system. In according to some exampleembodiments, the browser-executable code type cannot be natively run onthe database as it is configured as client-side script (e.g.,JavaScript) that can be used to quickly apply transformations to thesample dataset. Similarly, according to some example embodiments, thedatabase-executable code type cannot be natively run on the browserbecause the database-executable code type is code configured forfunctional programming (e.g., MapReduce) on a database backend, not aclient side browser.

As an example, assume a transformation to the sample dataset involveslocating a delimiter value and deleting values that appear before thedelimiter value (e.g., if the data is “firstName;lastName”, thetransformation would identify the delimiter “;” and delete the valuebefore the delimiter, which is the “firstName” value). Thetransformation engine 205 may apply the process to the sample datasetdirectly, locating the specified delimiter and removing values thatappear before the delimiter, and display the results directly in thedisplay of the client device. In contrast, upon the build command beingselected, the record engine 210 records the transformation as a taskthat may be applied in each node that manages each datastore (e.g.,datastore 122A, datastore 122B). For example, the record engine 210 mayrecord the task as part of a mapper code in a MapReduce sequence thatcan be applied across all the data stores concurrently (e.g., inparallel). Alternatively, according to some example embodiments, therecord engine 210 records the task as part of an Apache Spark job to beperformed by Spark workers across all data stores concurrently (e.g., inparallel).

The database engine 215 is configured to receive the transformation jobfrom the record engine 210 and apply the transformations to the raw datain the data stores 122A-N in database system 120. As discussed, thedatabase engine 215 may be implemented using different types of databasesystems (e.g., Apache Hadoop and HDFS, Oracle RDMS) and the recordengine 210 transforms the code applied to the sample dataset (which isconfigured to only apply the transformation to the small displayedsample dataset) into code that can be applied at very large scales bythe database engine 215.

The validation engine 225 manages validation logic for thetransformations applied to the raw data. As new raw data is received,the validation engine 225 retrieves the transformation job that wascreated by the record engine 210 and instructs the database engine 215to apply the transformation job to the new raw data to transform the newraw data into new structured data, to be added to the originallytransformed data stored in the data stores 122A-N. The process oftransforming new raw data into new structured data can be performedautomatically by the UI sample transformer 124 (e.g., via validationengine 225) without requiring the user to redo the transformations onthe sample dataset to create the transformation job. If an error isencountered while transforming the new raw data, the validation engine225 generates an error for the user to address. To address the error,the user may correct the faulty values in the new raw data, the user canchoose to ignore the error, or the user can create a new transformationtask to be included as part of the transformation job so that futureerrors are avoided.

In this way, an architect user (e.g., user 196) can quickly set up adistributed workflow that automatically transforms raw data intostructured data for analysis, and further ensure that new raw data isautomatically structured and added to the previous data. Other users,such as user 198, can analyze the structured data using the datavisualizer application 128. Because the potentially large set oftransformed data is handled on the backend (e.g., across data stores122A-122N), the analyst user 198 can quickly apply filters to the datato hone the data down to understandable results. To this end, theanalysis engine 220 is configured to generate filtered commands that thedatabase engine 215 can use to retrieve filtered data from data stores122A-N. Further, because new data is automatically transformed using thepre-configured transformation job, the analyst user 198 can simply use arefresh command to check whether new data has been added to the datastores 122A-N, instead of rerunning a transformation job on the entiredataset.

FIG. 3 illustrates a flow diagram for a method 300 of transforming largesets of data using the UI sample dataset-based approached, according tosome example embodiments. At operation 305, the UI sample transformer124 receives raw data (e.g., an input dataset) to be transformed. Insome example embodiments, the raw data is in non-validated form in thatfurther changes are required to make the data valid or parsable by thedata visualizer application 128. For example, the raw data may be inunstructured form (e.g., lists without delimiters, images). As a furtherexample, the raw data may have some structure, such as columns, but theuser still desires to transform the data to a desired structure so thatthat the data can be parsed and analyzed. The database engine 215 storesthe raw data in the database system 120 and partitions off a sample ofthe raw data to be displayed by the interface engine 200.

At operation 310, the transformation engine 205 receives one or moretransformations from the user (e.g., user 196). In response, thetransformation engine 205 applies the received transformations to thesample dataset, and displays the result on the data visualizerapplication 128. At operation 315, the UI sample transformer 124receives the build command from the user through the user interface. Atoperation 320, the record engine 210, in response to receiving the buildcommand, generates a transformation job that includes the one or moretransformations received at operation 310. In some embodiments, therecord engine 210 records the transformations by translating thetransformations from commands to be applied to the sample dataset (e.g.,command to be run on a single table) into commands that run on at alarge scale on database system 120, e.g., distributed database commands.At operation 325, the database engine 215 applies the transformation jobto the raw dataset to transform the raw dataset into a structuredformat. For instance, the transformation job applies each of thetransformations performed on the sample dataset to the raw dataset,thereby transforming the raw dataset into a structured dataset.

FIG. 4 shows a flow diagram for a method 400 of transforming new rawdata and validations, according to some example embodiments. Validationsare performed to ensure newer data is transformed by the transformationjob properly (e.g., so that the newly received data can be added to thealready transformed structured data in data stores 122A-N). An examplevalidation includes checking that certain types of data are in certainforms (e.g., check that a given column contains only string characters).A further example of a validation is checking whether values are withina given range (e.g., checking that the values in a given column arebetween a minimum and maximum value, checking that the values of a givencolumn are within some standard deviation value of the total values inthe column).

At operation 405, the UI sample transformer 124 receives new raw data tobe transformed. The database engine 215 automatically transfers (e.g.,upon receipt by the UI sample transformer 124) the new data to thedatabase system 120 for storage in data stores 122A-N. Because the rawdata is not yet structured, the newer raw data is stored in a stagingpartition in the data stores 122A-N.

In the example of FIG. 4, the new raw data is in the same or similarform as the original raw data for which the transformation job wascreated. In some embodiments, the new raw data is assumed to be in thesame form because the data was uploaded from the same source (e.g., useruploads more data to the transformation job project). In someembodiments, the user 196 determines that the newer data is in the sameor similar form as the original raw data and, accordingly, the user 196chooses the same transformation job (e.g., the transformation jobcreated to transform the original raw data) for application to the newerdata. In some example embodiments, the UI sample transformer 124 createsa project session for each transformation job, and if a user (e.g., user196) uploads the data to the project session, the UI sample transformer124 automatically applies the transformation job for that projectsession.

In some embodiments, the user (e.g., user 196) manually uploads the newraw data, and then manually selects the transformation job to be appliedto the new raw data. For example, the user may visually ascertain thatthe new raw data is in the same unstructured format as the original rawdata (e.g., the raw data received in operation 305, in FIG. 3) andaccordingly select the same transformation job (e.g., the transformationjob created at operation 320, of FIG. 3).

At operation 410, the database engine 215 applies the transformation jobto the new raw data stored in the staging partition of the data stores122A-N. At operation 420, if the database engine 215 encounters an errorwhen applying the transformation job to the new raw data, the error ispassed to the validation engine 225 for operation 425. For example, if atransformation to be applied is configured to identify a semi-colon as adelimiter, and a given value does not have a delimiter, the databaseengine 215 determines that validation has failed at operation 420because there is an error in the data (e.g., missing delimiter). Atoperation 425, the validation engine 225 receives the error (e.g., errordata received from database engine 215) and generates an error messagefor the user (e.g., user 196) to manage the error. In some exampleembodiments, the validation error is due to failure of a transformationtask. For example, if a transformation task specifies that a givencolumn is to have its values transformed from an integer data type tofloating point data type, and the column contains strings, then thetransformation task may fail as the database engine 215 may not beconfigured to transform strings to floating point data types.

To address a validation error, in some embodiments, the database engine215 ignores the error and the values that caused the error are left inuncorrected form in the newer transformed dataset. In some embodiments,the user corrects the values that caused the error (e.g., by deleting astray delimiter in the new raw data that caused an error). In someembodiments, particularly those where the error is widespread throughoutthe newer raw data, the transformation engine 205 receives from the user(e.g., user 196) a new transformation task to be included in thetransformation job to address the error, as illustrated at operation430. Once the error is handled (e.g., by correcting the error orcreating a new transformation) the transformation job is again reappliedto the newer raw data at operation 410.

At operation 435, if the database engine 215 does not encounter errorswhen applying the transformation job to the new raw data, the new rawdata is thereby transformed into new structured data, and is added tothe partition that stores the originally transformed raw data in datastores 122A-N.

Once the data is transformed into structured data and stored in databasesystem 120, the data visualizer application 128 allows users (e.g., user198) to quickly retrieve, filter, and analyze the information.Furthermore, in contrast to past approaches, because new raw data isautomatically transformed using the transformation job, the analyst user(e.g., user 198) does not have to run a full transformation jobhis/herself to analyze the latest data.

FIG. 5 shows a flow diagram for a method 500 of analyzing structureddata transformed using the approaches disclosed herein, according tosome example embodiments. At operation 505, the analysis engine 220receives an analysis request from an analyst user (e.g., user 198). Theanalysis request may be a request to filter out portions of thestructured data (e.g., return data only matching certain ranges) and/orvisualize the structured data using a data visualization graph (e.g.,social network graph, histogram).

At operation 510, the database engine 215 receives the analysis requestand applies operations of the analysis request to the structured data.For example, if the analysis request of operation 505 requests only rowshaving a value between a minimum and maximum, the database engine 215formulates a query configured to run on database system 120 andretrieves the matching rows from the structured data. The databaseengine 215 then transmits the matching rows to the analysis engine 220for further visualization or other operations specified in the analysisrequest. At operation 515, the analysis engine 220 displays therequested analysis results to the user through a display of the datavisualizer application 128.

As an illustrative example, and strictly as a non-limiting example,assume that the new raw data and all of operations of FIG. 4 occurredbetween operations 515 and 520 of FIG. 5. That is, assume that afterviewing the requested analysis data, newer data is received andtransformed using the transformation job, and further that thetransformed data is stored in the distributed database system 120.Continuing, further assume that at operation 520, the user (e.g., user198) wants to refresh the data to get the latest data for analysis.Conventionally, the user would have to run the transformation job on thenewly received data, or wait for other users with expertise to transformthe data. However, using the approach here, the transformation job wasquickly created using the sample-based approach. That is, throughverifying that the transformations produce the desired structured datausing a sample dataset, automatically applying the transformationsat-scale on the back end to transform the entire large dataset, andconstantly transforming newly received data using thesample-dataset-created transformation job, users of the data visualizerapplication 128 can transform and analyze data in an efficient, accurateway.

At operation 520, the analysis engine 220 receives an update requestfrom the analyst user (e.g., user 198). The update request is a type arefresh requests configured to check whether any new data has been addedto the data being analyzed (e.g., the transformed data stored in datastores 122A-N). At operation 525, the database engine 215 retrieves datamatching the operations of the analysis request. At operation 530, theanalysis engine 220 display the requested data using one or moregraphical data visualizations (e.g., network graph, point plot,histogram).

FIGS. 6A-6E depict example user interfaces for the UI sample transformer124, according to some embodiments. Although FIGS. 6A-6E depict specificexample user interfaces and user interface elements, these are merelynon-limiting examples; many other alternate user interfaces and userinterface elements can be generated by UI sample transformer 124 anddata visualizer application 128. It will be noted that alternatepresentations of the displays of FIGS. 6A-6E can include additionalinformation, graphics, options, and so forth. Alternatively, otherpresentations can include less information, or provide abridgedinformation for easy use by the user.

FIG. 6A shows a graphical user interface 600 for transforming dataaccording to some example embodiments. The user interface 600 includes acontrol menu 602 with display objects 604 a-e (e.g., buttons,drop-downs, fields) that are selectable by a user (e.g., user 196, user198) for uploading raw data, applying transformations, selecting filtersand graphical visualizations, and other operations discussed herein. Forinstance, display object 604 a can be configured as a data upload toolthat allows a user (e.g., user 196) to select raw data for upload to theapplication server 118 and UI sample transformer 124. As discussedabove, a sample dataset 606 of the raw data that represents theunstructured form of the data to be uploaded (e.g., the sample data issubset of the raw data that is stratified to accurately represent theraw dataset) is displayed within a portion of user interface 600. Theuser (e.g., user 196) can use transformation display objects 604 b and604 c to perform different transformations on the sample dataset 606.Though only two display objects are displayed as transformation displayobjects in FIG. 6A-E, it is appreciated that in some exampleembodiments, more transformation display objects can be included incontrol menu 602, in different menus and areas within user interface600, or as pop-up menus that appear upon selecting or visuallymanipulating data values within sample dataset 606. Display object(s)604 d can be options for graphical visualizations to be applied to thesample dataset 606 and/or the transformed full dataset. Thetransformations selected by the user (e.g., user 196) are displayed inthe transformation area 616. When a user (e.g., user 196) has completedtransformations of the sample dataset 606, he/she may select the builddisplay object 610 e, which triggers the record engine 210 to generate atransformation job from each of the applied transformations.

FIG. 6B shows the result of a first sample transformation on the sampledataset 606 through the user interface 600, according to some exampleembodiments. In the example shown in FIG. 6B, the user (e.g., user 196)defined that each row in the top row of the sample dataset 606 is aheader for the column of values below each top row value (e.g., the“name” value is a header for a column of name values for each of therows or entries below the top row). Consequently, transformation engine205 identifies the sample dataset 606 as a table with columns havingvalues set by the top row values. The first transformation is shown as afirst transformation task in the transformation area 616.

FIG. 6C shows the result of a second sample transformation on the sampledataset 606 through the user interface 600, according to some exampleembodiments. In the example shown in FIG. 6C, the user (e.g., user 196)combined two columns, the height column (“HT”) and the weight column(“WT)” into a single column, with the below values to be separated by asemi-colon delimiter (“;”). Consequently, as illustrated, the twocolumns are combined into a single column with the corresponding columnvalues per row separated by the semi-colon delimiter. The secondtransformation is shown as a second transformation task in thetransformation area 616.

FIG. 6D shows the result of a third sample transformation on the sampledataset 606 through the user interface 600, according to some exampleembodiments. In the example shown in FIG. 6D, the user (e.g., user 196)removed rows that have the value of “NL” in the “Country” column.Consequently, as shown in FIG. 6D, the second row (which contained datafor the person “H. Lorentz”) has been removed, as that entry has “NL” inthe country column. The third transformation is shown as a thirdtransformation task in the transformation area 616.

FIG. 6E shows the result of a fourth sample transformation on the sampledataset 606 through the user interface 600, according to some exampleembodiments. In the example shown in FIG. 6E, the user (e.g., user 196)used a find and replace transformation to find and replace any value inthe column “Country” that matches “GB” and replace the value with thevalue “UK”. Consequently, as shown in FIG. 6E, the first, third,seventh, and eight columns have their column values replaced per thetransformation. The fourth transformation is shown as a fourthtransformation task (e.g., validation transformation) in thetransformation area 616.

After the user 196 is finished transforming the sample dataset 606, theuser 196 selects the build display object 610 e. In response to thebuild display object 610 e being selected, the record engine 210identifies each of the transformations tasks (e.g., validationtransformations) applied to the sample dataset 606 and generates atransformation job in code that is configured to run on the backend, atscale (e.g., runnable in parallel across data stores 122A-N). The recordengine 210 then passes the transformation job code to the databaseengine 215, which applies the transformation job to raw data in thedatabase system 120 to transform the raw data to structured data thatmatches the changes made to the sample dataset 606.

FIG. 7 shows a network interaction diagram 700 showing networkinteractions for UI sample dataset-based transformations to large setsof data, according to some embodiments. As illustrated, the computingentities include the client device 106, which runs the data visualizerapplication 128, which communicates over network 102 (represented by avertical dashed line) to the application server 118, which hosts the UIsample transformer 124, and which further issues instructions to thedatabase system 124 over a network (represented by an additionalvertical dashed line).

At operation 705, using the client device 106, the user 196 uploads theraw dataset to the application server 118. At operation 710, the UIsample transformer 124 (e.g., the database engine 215) stores theuploaded raw data to the network-based data analysis system 104. Atoperation 715, the network-based data analysis system 104 receives theraw dataset from the UI sample transformer 124 and stores it in adatabase, e.g., in distributed form across data stores 122A-N.

At operation 750, the database engine 215 generates a sample dataset ofthe uploaded raw data for UI-based transformations. According to someexample embodiments, the sample dataset should be small enough tomaintain responsiveness in a UI on client device 106. For example, thesample dataset may comprise all of the columns (e.g., schema) for agiven dataset but only a small number of rows (e.g., less than 100). Inthis way, the transformations applied to the sample dataset will yieldthe same results when applied to the large raw dataset because thesample dataset accurately reflects the schema structure of the rawdataset, but only over a few rows.

At operation 755, the client device 106 displays the sample dataset, asillustrated in FIG. 6A. At operation 760, the user 196 applies one ormore transformations to the dataset, as illustrated in FIGS. 6B-6E. Atoperation 765, in response to the user 196 selecting the build displayobject 610 e, the record engine 210 generates a transformation jobconfigured to run on the network-based data analysis system 104. Atoperation 770, the database engine 215 receives the transformation jobcode and applies the transformation job to the raw data in thenetwork-based data analysis system 104. For example, the network-baseddata analysis system 104 receives instructions from the database system120 and applies the transformations on the raw data across the datastores 122A-N in parallel.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules can constitute eithersoftware modules (e.g., code embodied on a machine-readable medium) orhardware modules. A “hardware module” is a tangible unit capable ofperforming certain operations and can be configured or arranged in acertain physical manner. In various example embodiments, one or morecomputer systems (e.g., a standalone computer system, a client computersystem, or a server computer system) or one or more hardware modules ofa computer system (e.g., a processor or a group of processors) can beconfigured by software (e.g., an application or application portion) asa hardware module that operates to perform certain operations asdescribed herein.

In some embodiments, a hardware module can be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module can include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module can be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware module may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware modulecan include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwaremodules become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware module mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) can be driven by cost and time considerations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware module at one instance oftime and to constitute a different hardware module at a differentinstance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules can be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications can be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module can perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module can then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules can also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein can beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein can be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method can be performed by one or more processors orprocessor-implemented modules. Moreover, the one or more processors mayalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)).

The performance of certain of the operations may be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example embodiments, the processorsor processor-implemented modules can be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented modules are distributed across a number ofgeographic locations. The modules, methods, applications and so forthdescribed in conjunction with FIGS. 1-7 are implemented in someembodiments in the context of a machine and an associated softwarearchitecture. The sections below describe representative softwarearchitecture and machine (e.g., hardware) architecture that are suitablefor use with the disclosed embodiments.

FIG. 8 is a block diagram illustrating components of a machine 800,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 8 shows a diagrammatic representation of the machine800 in the example form of a computer system, within which instructions816 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 800 to perform any one ormore of the methodologies discussed herein can be executed. For example,the instructions 816 can cause the machine 800 to execute the flowdiagrams of FIGS. 3-5 and network interaction diagram of FIG. 7.Additionally, or alternatively, the instructions 816 can implement theinterface engine 200, transformation engine 205, record engine 210,database engine 215, analysis engine 220, and validation engine 225 ofFIG. 2, and so forth. The instructions 816 transform the general,non-programmed machine into a particular machine 800 programmed to carryout the described and illustrated functions in the manner described. Inalternative embodiments, the machine 800 operates as a standalone deviceor can be coupled (e.g., networked) to other machines. In a networkeddeployment, the machine 800 may operate in the capacity of a servermachine or a client machine in a server-client network environment, oras a peer machine in a peer-to-peer (or distributed) networkenvironment. The machine 800 can comprise, but not be limited to, aserver computer, a client computer, a personal computer (PC), a tabletcomputer, a laptop computer, a netbook, a set-top box (STB), a personaldigital assistant (PDA), an entertainment media system, a cellulartelephone, a smart phone, a mobile device, a wearable device (e.g., asmart watch), a smart home device (e.g., a smart appliance), other smartdevices, a web appliance, a network router, a network switch, a networkbridge, or any machine capable of executing the instructions 816,sequentially or otherwise, that specify actions to be taken by themachine 800. Further, while only a single machine 800 is illustrated,the term “machine” shall also be taken to include a collection ofmachines 800 that individually or jointly execute the instructions 816to perform any one or more of the methodologies discussed herein.

The machine 800 can include processors 810, memory/storage 830, and I/Ocomponents 850, which can be configured to communicate with each othersuch as via a bus 802. In an example embodiment, the processors 810(e.g., a Central Processing Unit (CPU), a Reduced Instruction SetComputing (RISC) processor, a Complex Instruction Set Computing (CISC)processor, a Graphics Processing Unit (GPU), a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), aRadio-Frequency Integrated Circuit (RFIC), another processor, or anysuitable combination thereof) can include, for example, processor 812and processor 814 that may execute instructions 816. The term“processor” is intended to include multi-core processor that maycomprise two or more independent processors (sometimes referred to as“cores”) that can execute instructions 816 contemporaneously. AlthoughFIG. 8 shows multiple processors 810, the machine 800 may include asingle processor with a single core, a single processor with multiplecores (e.g., a multi-core processor), multiple processors with a singlecore, multiple processors with multiples cores, or any combinationthereof.

The memory/storage 830 can include a memory 832, such as a main memory,or other memory storage, and a storage unit 836, both accessible to theprocessors 810 such as via the bus 802. The storage unit 836 and memory832 store the instructions 816 embodying any one or more of themethodologies or functions described herein. The instructions 816 canalso reside, completely or partially, within the memory 832, within thestorage unit 836, within at least one of the processors 810 (e.g.,within the processor's cache memory), or any suitable combinationthereof, during execution thereof by the machine 800. Accordingly, thememory 832, the storage unit 836, and the memory of the processors 810are examples of machine-readable media.

As used herein, the term “machine-readable medium” means a device ableto store instructions and data temporarily or permanently and mayinclude, but is not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, optical media, magneticmedia, cache memory, other types of storage (e.g., Erasable ProgrammableRead-Only Memory (EEPROM)) or any suitable combination thereof. The term“machine-readable medium” should be taken to include a single medium ormultiple media (e.g., a centralized or distributed database, orassociated caches and servers) able to store instructions 816. The term“machine-readable medium” shall also be taken to include any medium, orcombination of multiple media, that is capable of storing instructions(e.g., instructions 816) for execution by a machine (e.g., machine 800),such that the instructions, when executed by one or more processors ofthe machine 800 (e.g., processors 810), cause the machine 800 to performany one or more of the methodologies described herein. Accordingly, a“machine-readable medium” refers to a single storage apparatus ordevice, as well as “cloud-based” storage systems or storage networksthat include multiple storage apparatus or devices. The term“machine-readable medium” excludes signals per se.

The I/O components 850 can include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 850 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components 850can include many other components that are not shown in FIG. 8. The I/Ocomponents 850 are grouped according to functionality merely forsimplifying the following discussion, and the grouping is in no waylimiting. In various example embodiments, the I/O components 850 caninclude output components 852 and input components 854. The outputcomponents 852 can include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 854 can include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and force of touches or touch gestures, orother tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 850 can includebiometric components 856, motion components 858, environmentalcomponents 860, or position components 862 among a wide array of othercomponents. For example, the biometric components 856 can includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 858 can includeacceleration sensor components (e.g., an accelerometer), gravitationsensor components, rotation sensor components (e.g., a gyroscope), andso forth. The environmental components 860 can include, for example,illumination sensor components (e.g., a photometer), temperature sensorcomponents (e.g., one or more thermometers that detect ambienttemperature), humidity sensor components, pressure sensor components(e.g., a barometer), acoustic sensor components (e.g., one or moremicrophones that detect background noise), proximity sensor components(e.g., infrared sensors that detect nearby objects), gas sensorcomponents (e.g., machine olfaction detection sensors, gas detectionsensors to detect concentrations of hazardous gases for safety or tomeasure pollutants in the atmosphere), or other components that mayprovide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 862 caninclude location sensor components (e.g., a Global Positioning System(GPS) receiver component), altitude sensor components (e.g., altimetersor barometers that detect air pressure from which altitude may bederived), orientation sensor components (e.g., magnetometers), and thelike.

Communication can be implemented using a wide variety of technologies.The I/O components 850 may include communication components 864 operableto couple the machine 800 to a network 880 or devices 870 via a coupling882 and a coupling 872, respectively. For example, the communicationcomponents 864 include a network interface component or other suitabledevice to interface with the network 880. In further examples,communication components 864 include wired communication components,wireless communication components, cellular communication components,Near Field Communication (NFC) components, BLUETOOTH® components (e.g.,BLUETOOTH® Low Energy), WI-FI® components, and other communicationcomponents to provide communication via other modalities. The devices870 may be another machine or any of a wide variety of peripheraldevices (e.g., a peripheral device coupled via a Universal Serial Bus(USB)).

Moreover, the communication components 864 can detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 864 can include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as a Universal Product Code (UPC) barcode, multi-dimensional bar codes such as a Quick Response (QR) code,Aztec Code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code,Uniform Commercial Code Reduced Space Symbology (UCC RSS)-2D bar codes,and other optical codes), acoustic detection components (e.g.,microphones to identify tagged audio signals), or any suitablecombination thereof. In addition, a variety of information can bederived via the communication components 864, such as location viaInternet Protocol (IP) geo-location, location via WI-FI® signaltriangulation, location via detecting a BLUETOOTH® or NFC beacon signalthat may indicate a particular location, and so forth.

In various example embodiments, one or more portions of the network 880can be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a WI-FI®network, another type of network, or a combination of two or more suchnetworks. For example, the network 880 or a portion of the network 880may include a wireless or cellular network, and the coupling 882 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling 882 can implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 816 can be transmitted or received over the network 880using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components864) and utilizing any one of a number of well-known transfer protocols(e.g., Hypertext Transfer Protocol (HTTP)). Similarly, the instructions816 can be transmitted or received using a transmission medium via thecoupling 872 (e.g., a peer-to-peer coupling) to devices 870. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying the instructions 816for execution by the machine 800, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the inventive subject matter may be referred to herein, individuallyor collectively, by the term “invention” merely for convenience andwithout intending to voluntarily limit the scope of this application toany single disclosure or inventive concept if more than one is, in fact,disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

1. (canceled)
 2. A system comprising: one or more computer processors;and one or more computer-readable mediums storing instructions that,when executed by the one or more computer processors, cause the systemto perform operations comprising: receiving a request to apply a set ofdata transformations to convert an input data set into a validatedformat that can be parsed by a data visualization application; executingthe set of data transformations on a sample dataset that is a subset ofthe input data set, wherein executing the set of data transformationsyields one or more errors; causing presentation of data identifying theone or more errors; receiving one or more additional datatransformations to convert the dataset into the validated format;executing an updated set of data transformations to the sample data set,the updated set of data transformations being based on the set of datatransformations and the one or more additional data transformations,wherein execution of the updated set of data transformations completeswithout error; and executing the updated set of data transformations onthe input dataset to convert the input dataset into the validatedformat.
 3. The system of claim 2, the operations further comprising:receiving the input data set in a non-validated format that cannot beparsed by the data visualization application.
 4. The system of claim 2,the operations further comprising: generating database-executable codedefining the updated set of data transformations based onbrowser-executable code defining the data transformations, thebrowser-executable code having been used to execute the updated set ofdata transformations to the sample data set.
 5. The system of claim 2,wherein the data visualization application is configured to parse theinput data in the validated format to cause a visualization of the inputdata, the visualization including at least one of: a point plot, anetwork graph, or a histogram.
 6. The system of claim 2, the operationsfurther comprising: receiving an additional input dataset in thenon-validated format; and in response to receiving the additional inputdataset, automatically executing the updated set of data transformationsto convert the additional input dataset into the validated format. 7.The system of claim 6, the operations further comprising: receiving arequest to filter a portion of the input dataset that is in thevalidated format; in response to receiving the request, generating afirst filtered dataset extracted from the input dataset that is in thevalidated format; receiving a refresh request for the first filtereddataset; and in response to receiving the refresh request, generating asecond filtered dataset that includes validated data from the additionalinput dataset in the validated format.
 8. The system of claim 2, whereinthe set of data transformations and the one or more additional datatransformations are received via a graphical user interface (GUI)comprising one or more display objects that are configured to initiatepre-configured transformations to datasets using a browser-executablecode type upon the one or more display objects being selected throughthe GUI.
 9. A method comprising: receiving a request to apply a set ofdata transformations to convert an input data set into a validatedformat that can be parsed by a data visualization application; executingthe set of data transformations on a sample dataset that is a subset ofthe input data set, wherein executing the set of data transformationsyields one or more errors; causing presentation of data identifying theone or more errors; receiving one or more additional datatransformations to convert the dataset into the validated format;executing an updated set of data transformations to the sample data set,the updated set of data transformations being based on the set of datatransformations and the one or more additional data transformations,wherein execution of the updated set of data transformations completeswithout error; and executing the updated set of data transformations onthe input dataset to convert the input dataset into the validatedformat.
 10. The method of claim 9, further comprising: receiving theinput data set in a non-validated format that cannot be parsed by thedata visualization application.
 11. The method of claim 9, furthercomprising: generating database-executable code defining the updated setof data transformations based on browser-executable code defining thedata transformations, the browser-executable code having been used toexecute the updated set of data transformations to the sample data set.12. The method of claim 9, herein the data visualization application isconfigured to parse the input data in the validated format to cause avisualization of the input data, the visualization including at leastone of: a point plot, a network graph, or a histogram.
 13. The method ofclaim 9, further comprising: receiving an additional input dataset inthe non-validated format; and in response to receiving the additionalinput dataset, automatically executing the updated set of datatransformations to convert the additional input dataset into thevalidated format.
 14. The method of claim 13, further comprising:receiving a request to filter a portion of the input dataset that is inthe validated format; in response to receiving the request, generating afirst filtered dataset extracted from the input dataset that is in thevalidated format; receiving a refresh request for the first filtereddataset; and in response to receiving the refresh request, generating asecond filtered dataset brat includes validated data from the additionalinput dataset in the validated format.
 15. The method of claim 9,wherein the set of data transformations and the one or more additionaldata transformations are received via a graphical user interface (GUI)comprising one or more display objects that are configured to initiatepre-configured transformations to datasets using a browser-executablecode type upon the one or more display objects being selected throughthe GUI.
 16. A non-transitory computer-readable medium storinginstructions that, when executed by one or more computer processors ofone Or more computing devices, cause the one or more computing devicesto perform operations comprising: receiving a request to apply a set ofdata transformations to convert an input data set into a validatedformat that can be parsed by a data visualization application; executingthe set of data transformations on a sample dataset that is a subset ofthe input data set, wherein executing the set of data transformationsyields one or more errors; causing presentation of data identifying theone or more errors; receiving one or more additional datatransformations to convert the dataset into the validated format;executing an updated set of data transformations to the sample data set,the updated set of data transformations being based on the set of datatransformations and the one or more additional data transformations,wherein execution of the updated set of data transformations completeswithout error; and executing the updated set of data transformation onthe input dataset to convert the input dataset into the validatedformat.
 17. The non-transitory computer-readable medium of claim 16, theoperations further comprising: receiving the input data set in anon-validated format that cannot be parsed by the data visualizationapplication.
 18. The non-transitory computer-readable medium of claim16, the operations further comprising: generating database-executablecode defining the updated set of data transformations based onbrowser-executable code defining the data transformations, thebrowser-executable code having been used to execute the updated set ofdata transformations to the sample data set.
 19. The non-transitorycomputer-readable medium of claim 16, wherein the data visualizationapplication is configured to parse the input data in the validatedformat to cause a visualization of the input data, the visualizationincluding at least one of: a point plot, a network graph, or ahistogram.
 20. The non-transitory computer-readable medium of claim 16,the operations further comprising: receiving an additional input datasetin the non-validated format; and in response to receiving the additionalinput dataset, automatically executing the updated set of datatransformations to convert the additional input dataset into thevalidated format.
 21. The non-transitory computer-readable medium ofclaim 20, the operations further comprising: receiving a request tofilter a portion of the input dataset that is in the validated format;in response to receiving the request, generating a first filtereddataset extracted from the input dataset that is in the validatedformat; receiving a refresh request for the first filtered dataset; andin response to receiving the refresh request, generating a secondfiltered dataset that includes validated data from the additional inputdataset in the validated format.